Γùè This utility is distributed as shareware: if you like it please honor the shareware system by sending $5 to the author at the address above. Since cashing international cheques is very expensive, please send cash only (U.S. dollars are best, but any other currency is fine).
Γùè If you work on the Macintosh, there are many things you can send me instead of the money. Here are some suggestions: original software (but don't send any shareware/freeware unless you're the author), books or computer-related magazines (any free issue or subscription is welcome), CD-ROMs, any piece of new or used hardware, or anything else you've created.
Γùè There's still another thing you could do: I'll finish my physics studies sometime in 1996 and I'm looking for a one-year job as a programmer (or maybe a scientist?) outside of Italy. Let me know if you have anything to offer.
Γùè If you can't afford any of the above an e-mail, a postcard or a letter is welcome. I speak English, French and Italian. Please forgive me if I don't answer to all of your letters - I am often overloaded with my school work.
ΓÇó Introduction
Γùè PowerPCheck is a cool drag & drop utility that looks for native PowerPC code inside applications, control panels, extensions and all other executable files. It can check individual files as well as folders or entire disks; it inspects both the data fork and the resource fork of each file and creates a detailed text report of all the native code it finds. Version 3.0 can also remove the PowerPC or 68K code from the inspected files.
ΓÇó Removing code
Γùè PowerPCheck can remove unused code from the files it inspects. This operation is potentially dangerous because some programs may stop working or even crash if you remove some code that they expect to find in their own files.
Γùè The PowerPC application code stored in the data fork can usually be removed without disturbing the 68K application; the stripped application should still run on both PowerPC and 68K Macs, although it will be a lot slower when running on a Power Mac. This is not guaranteed to work, but itΓÇÖs the safest removal you can choose.
Γùè The PowerPC code stored in resource forks is a lot more dangerous to remove, since itΓÇÖs usually directly accessed by the related application. The stripped program will most likely run on a 68K Mac, but it may easily crash or stop working if you move it to a Power Mac.
Γùè Removing the 68K code from the resource fork of an application always prevents it from running on a 68K Macintosh. The application should still be able to run on a Power Mac, but youΓÇÖll get an error message from the Finder if you try to launch it on a 68K machine. Note that this kind of removal can only be done on applications that carry native PowerPC code in their data forks.
Γùè Before attempting to remove any kind of code, please make sure you have a backup copy of all your applications, plug-ins, extensions, control panels and shared libraries. Code removal can help if you have a 68K Mac and a small hard disk filled with megabytes of unused PowerPC code, but stripped-down programs canΓÇÖt be restored to their original state if you donΓÇÖt have a clean backup copy somewhere on your shelves.
ΓÇó Technical information
Γùè There are two kinds of resources that contain native PowerPC code: pure code resources only contain what is called a code fragment, while accelerated and fat resources have a routine descriptor as well. This has nothing to do with performance and doesnΓÇÖt affect end users, but programmers may be interested in this topic; PowerPCheck marks with an asterisk all code resources that have a routine descriptor.
Γùè PowerPCheck uses a simple method to speed up file scanning: the 'TYP#' 128 resource contains a list of file types to skip, and the 'TYP#' 129 resource contains a list of resource types to skip. You may add (or remove) file and resource types with ResEdit if you know what youΓÇÖre doing. Note that PowerPCheck also skips all files that have an empty resource fork.
ΓÇó Version history
Γùè 3.0.1 - Recompiled with CodeWarrior 7.
Γùè 3.0 - PowerPCheck can now remove the PowerPC or 68K code from the inspected files.
Γùè 2.1 - This version is faster, requires less memory and can work in the background. Fixed various interface and file-saving issues.
Γùè 2.0 - First shareware release; rewritten from scratch, now scans folders and disks and inspects resources.
Γùè 1.2.1 - Cleaned up the code and updated documentation.
Γùè 1.2 - Fat version! Runs native on Power Macs.
Γùè 1.1 - Rebuilt with new versions of the compiler (never released).
Γùè 1.0 - First public release.
ΓÇó Distribution
◊ PowerPCheck is ©1994-95 Alessandro Levi Montalcini. It can be freely distributed as long as it is not modified and there’s no charge for it, but it may not be included in any commercial package without my consent.
Γùè You may find the latest version of all my shareware programs by anonymous ftp to ftp.alpcom.it, inside the /software/mac/LMontalcini directory. The complete ShareDisk package, which contains all my stuff and can be registered at a very low price, is also available there.
Γùè All online services and bulletin boards may make it available to their users at no charge other than the normal connection fees.
Γùè All non-profit user groups may distribute it at no charge.
Γùè All magazines may publish it on floppy disk without asking me first, as long as I get a copy of the issue containing my software.
Γùè All CD-ROM shareware collections and CD-ROM magazines may include it without my prior consent, as long as I get either a copy of the CD-ROM or an offer to buy the CD-ROM at a discounted price.
Γùè All redistribution companies such as Educorp may distribute it, as long as I get a copy of each media containing my software and a catalog of the companyΓÇÖs offerings (where applicable).
ΓÇó Disclaimer
Γùè PowerPCheck shouldnΓÇÖt cause any damage, but youΓÇÖre using it at your own risk. As an independent software developer, I can make no warranties whatsoever on it.
ΓÇó Have fun!
Γùè And don't forget to $$$ send your contribution $$$ so that more cool utilities will see the light in the near future, at the low-low-low costs of shareware.
